Proofreading Tagging Guide (Protocol Update)

Proofreading Tags: When to 
Use Each One

Ripped Area
Ripped Area tag is used when the cell leaves or enters from the edge of the dataset, OR when a break occurs at an area of ripped or 
torn data. But, only mark ripped area cells “backbone proofread” if they enter or leave the dataset, NOT if they break at an area of 
ripped or torn data.
Ripped Area tag is NOT used when the cell is “Can’t Trace to Soma”, whether the cell leaves the brain or not.
Important: Neurons tagged "Ripped Area" only receive "Backbone Proofread" label if the rip occurs where the neuron leaves 
or enters the dataset. If the rip is inside the brain, the neuron is tagged "Ripped Area" but does not receive the "Backbone 
Proofread" label.

Done
The “Done” tag represents a completed task with no major interference from errors or unusual circumstances. A cell tagged as 
“Done” has been fully proofread according to the current task expectations.
Because each dataset and assignment may have slightly different goals, the exact criteria for “Done” can vary based on the 
instructions and parameters provided for that task. If you are unsure whether a cell meets the current “Done” criteria, ask the task 
giver or a senior proofreader before finalizing the tag.
Important: Neurons tagged “Done” should also receive the “Backbone Proofread” label in banc-bot.

Can’t Fix
Similar to the “Done” tag, “Can’t Fix” represents the opposite outcome: the cell cannot be completed under the current task 
parameters. This does not necessarily mean the work in the final link is unproofread—rather, it means the cell cannot be brought to a 
complete, acceptable endpoint for the assignment.
Most commonly, this happens due to issues such as slide damage, misalignments/jumps, or dissolved/missing tissue that prevent 
reliable continuation of the trace only when there is clearly more data after the false termination within the brain and the segment 
does not leaving the brain.
In addition, “Can’t Fix” can be used when the effort required is not worth the time cost, even if the cell might technically be 
solvable. Some neurons may be possible to finish, but if the proofreading time needed is excessive relative to the expected value of the 
result, they can still be marked “Can’t Fix.” This threshold is flexible and may vary depending on the task goals and the expectations 
set by the task giver.
If you’re unsure whether a difficult cell meets the current threshold for “Can’t Fix,” ask the task giver (or a senior proofreader) what the 
expected time/effort cutoff is for that assignment.
Important: Neurons tagged “Can’t Fix” should NOT receive the “Backbone Proofread” label.

Can’t Trace to Soma
“Can’t Trace To Soma” is different from “Can’t Fix.” This tag should be used when the neuron is essentially fully reconstructed, 
and the only remaining missing portion (as best as the proofreader can determine) is the soma tract and soma. In other words, the 
backbone of the cell is complete, but locating or confirming the soma path is not feasible within a reasonable amount of time.
Important: Neurons tagged “Can’t Trace To Soma” should still receive the “Backbone Proofread” label.

Need 2nd Opinion
Similar to the “Done” and “Can’t Fix” tags, “Need 2nd Opinion” is a middle-ground option. Use this tag when you believe the cell is 
likely solvable, but there are one or more difficult areas where you are unsure how to proceed or want confirmation before making a 
final call.
Cells marked “Need 2nd Opinion” are intended to be reviewed by another member of the team (coworkers and/or senior 
proofreaders). After review and consensus, the tag should be updated to whatever is most appropriate based on the outcome—most 
commonly “Done” or “Can’t Fix.”
Important: “Need 2nd Opinion” is a temporary tag. It is not meant to be the final state of a cell at the end of an assignment. Before 
the assignment is considered complete, these cells should be revisited, the tag should be changed to the correct final outcome, 
and the appropriate labeling step should be applied (for example, adding “Backbone Proofread” if the final outcome is Done).

Already Proofread
This tag is used when the proofreader has done their due diligence, investigated the cell, and determined that no corrections or 
additional proofreading work are needed. This can happen when task lists are refined and a few already-proofread cells get mixed 
in.
Checking whether the cell already has a “Backbone Proofread” label in banc-bot can be a helpful indicator that someone may have 
worked on it, but it does not replace verification—you won’t have the full picture until you inspect the neuron yourself.
Please be careful and proofread the cell normally before using this tag, and only apply “Already Proofread” once you are 
confident there is truly nothing left to fix.
Important: If you do make edits to a cell that already has a “Backbone Proofread” label (even small changes like splits), re-check the 
label status afterward. Some edits can change the cell ID or seed supervoxel association, which may result in the neuron no longer 
carrying the Backbone Proofread label. If changes were made, the cell should receive a new “Backbone Proofread” label from the 
proofreader who performed the edits (or at minimum, the label should be verified in banc-bot again) before tagging it in the sheet.

Work In Progress (WIP)
This tag is used as a temporary marker to indicate the proofreader has paused work on a cell before it is complete. WIP is intended 
strictly for workflow tracking (for example, when taking a break, switching tasks, or stopping for the day).
This tag should only be used temporarily and must be replaced with the appropriate final tag once the cell is finished (e.g., Done, 
Can’t Fix, Need 2nd Opinion, etc.).
Important: Cells should not remain marked as “WIP” in the sheet at the end of an assignment.

Not A Neuron
This tag is used for tasks where the provided cell ID or coordinates lead to a small, insignificant fragment rather than a 
reconstructable neuron. These fragments typically lack major branches and do not contain meaningful synaptic structure, so they 
are not treated as valid neurons for proofreading purposes.
Examples include mitochondria, tiny neurite debris, extracellular space, glial fragments, resin bubbles, and other small imaging 
or segmentation artifacts.
Clarification: A small starting seed does not automatically mean the task is “Not a Neuron.” You should still make a reasonable 
attempt to determine whether it connects into a real neuron. However, if it is clearly just a fragment (for example: a glial shred that 
expands into a large merger, a mitochondrion, or an isolated artifact), and attaching it would add no meaningful structure (e.g., “only” a 
mitochondrion onto an already completed cell), then it is appropriate to tag it as Not a Neuron and move on.
Important: Neurons tagged “Not a Neuron” should not receive the “Backbone Proofread” label.

NoneType Error
This tag is used when a cell cannot be completed due to a technical/tool error in Spelunker. Most commonly, this happens when 
the Merge button or Split button fails to function (often producing a NoneType error or similar behavior).
In some cases, the cell’s final link may still appear to contain all the components of a complete neuron, but the task cannot be finalized 
properly because required actions (merges/splits) cannot be performed. In other cases, the cell cannot be completed because a 
merger cannot be split off, preventing clean reconstruction.
Important: Neurons tagged “NoneType Error” should not receive the “Backbone Proofread” label.
Side note: This issue appears to be version-dependent, and may not occur in some versions of Spelunker. As far as we know, it is 
currently being worked on.

Can’t Un-submit to Banc-Bot (Outdated)
This tag was used when a proofreader determined that a cell previously submitted to banc-bot needed to be un-submitted (most 
commonly because it needed to be reclassified, such as changing it to “Can’t Fix”).
Due to how the labeling system works, the “Backbone Proofread” submission could only be un-submitted by the same person who 
originally submitted it. This restriction acted as a safety measure to help protect the integrity and traceability of our labeling workflow.
Side note: This tag is now rarely used, since recent backend/workflow changes have largely removed the need for this situation.

Un-Submitted to Banc-Bot (Outdated)
This tag was used to indicate that a previously submitted banc-bot label (such as “Backbone Proofread”) was successfully removed 
by the original submitter. This tag only confirms that the label was taken off—it does not necessarily mean a new or replacement tag 
has already been applied.
Side note: This tag is now outdated, since the updated backend/workflow no longer requires individuals to manually remove labels in 
this way.